-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Support React v15 on legacy v0.13 branch #3607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I want to delete this branch but I don't want the code to go away forever 😛 e.g. even if I close this PR, I can use the PR to restore the branch! 😄 |
This would be great to get a release of! |
@ljharb Can you let me know if this code actually works though? I have no way of checking. |
I can only confirm it works secondhand atm, but by tomorrow I'll have first-hand confirmation :-) |
@ljharb ping |
@taion sorry; i've been traveling. I believe @goatslacker has verified that this works beautifully, but hopefully he can chime in :-) |
@taion been traveling as well, yeah the change works well. |
Any objections to releasing this? |
No, go for it. |
That was meant for @timdorr 😄 |
Sorry, having to swap out some production systems on the fly at work, so I've been running around like a chicken with my head cut off all day. Haven't even eaten lunch :( LGTM. Worst case you can yank the version if it's bad. |
Sorry! Just wanted to make sure your "but why?" was addressed. (: |
It was more of a joking "why reach into the past" kind of thing. No worries :) |
Thanks for your work on this! |
I can confirm that 13.4 worked without these changes on 15.4. This seems to be mostly fixes to the unit tests. There is one fix that needs to be addressed in the Link component that wasn't addressed, that is a warning for applying additional props onto the a tag in the render func. |
Ugh okay this is released as v0.13.6. I vote that we should just delete the |
Agreed. I'll go nuke it into oblivion now. |
Deleting published code is not so good :-( please don't do that, even if there won't be further releases. |
Well, the former tip of the 0.13.x branch and the v0.13.6 tag are the same. I don't think we should delete the tag. No code is gone. |
It's not deleted. Only the branch is gone. The tag remains: https://github.com/reactjs/react-router/tree/v0.13.6 |
I believe they are talking about just deleting the branch not the tag.
|
Just making sure, thanks :-) |
I was going through cleaning up old branches, and realized I still had this one sitting around.
Might as well check it in? I think it works.
From #3281, but looks like nobody's desperately in need of a release or anything.